Skip to content

Fix #3471: Avoid wrong flag kind when desugaring module definitions #3486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 16, 2017

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Nov 16, 2017

No description provided.

@@ -0,0 +1 @@
sealed object Fun
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we also print a warning saying that the modifier is useless here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't do it for final either. If we solve it we should solve it for both at the same time. But not that scalac does not warn for final object either.

Copy link
Contributor

@nicolasstucki nicolasstucki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though we should add a warning

@nicolasstucki
Copy link
Contributor

Now tests fail for inline object :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants